Creating a network slice selection policy rule

ABSTRACT

Apparatuses, methods, and systems are disclosed for creating a network slice section policy (“NSSP”) rule. One apparatus includes a processor and a transceiver for communicating with a network function in a mobile communication network. The processor receives a first request from the network function, the first request comprising a list of one or more application identifiers and a corresponding application profile and application provider for each application identifier. The processor determines one or more network slice identifiers for each application identifier using the corresponding application profile and application provider. The processor also creates a NSSP rule for each application identifier in the list of application identifiers, the NSSP rule containing the application identifier and the associated one or more network slice identifiers.

FIELD

The subject matter disclosed herein relates generally to wirelesscommunications and more particularly relates to creating a NSSP rulebased on an application identifier and corresponding application profileand application provider.

BACKGROUND

The following abbreviations and acronyms are herewith defined, at leastsome of which are referred to within the following description.

Third Generation Partnership Project (“3GPP”), Access and MobilityManagement Function (“AMF”), Application Function (“AF”), Downlink(“DL”), Enhanced Mobile Broadband (“eMBB”), Evolved Node B (“eNB”),European Telecommunications Standards Institute (“ETSI”), FrequencyDivision Duplex (“FDD”), Frequency Division Multiple Access (“FDMA”),Hybrid Automatic Repeat Request (“HARQ”), Internet Protocol (“IP”),Internet-of-Things (“IoT”), Long Term Evolution (“LTE”), LTA Advanced(“LTE-A”), Medium Access Control (“MAC”), Multiple Access (“MA”),Mobility Management Entity (“MME”), Machine Type Communication (“MTC”),Massive MTC (“mMTC”), Narrowband (“NB”), Network Exposure Function(“NEF”), Network Function (“NF”), Network Slice Selection AssistanceInformation (“NSSAI”), Network Slice Selection Policy (“NSSP”), NextGeneration Node B (“gNB”), Packet Data Unit (“PDU”), Policy ControlFunction (“PCF”), Public Land Mobile Network (“PLMN”), Quality ofService (“QoS”), Radio Access Network (“RAN”), Radio Resource Control(“RRC”), Session Management Function (“SMF”), Single-Network SliceSelection Assistance Information (“S-NSSAI”), Transmission ControlProtocol (“TCP”), Time-Division Duplex (“TDD”), Time Division Multiplex(“TDM”), Transmission and Reception Point (“TRP”), Transmit (“TX”),Unified Data Management (“UDM”), User Data Repository (“UDR”), UserDatagram Protocol (“UDP”), User Entity/Equipment (Mobile Terminal)(“UE”), Ultra-Reliability and Low Latency Communications (“URLLC”),Uplink (“UL”), Universal Mobile Telecommunications System (“UMTS”), UserPlane Function (“UPF”), and Worldwide Interoperability for MicrowaveAccess (“WiMAX”). As used herein, “HARQ-ACK” may represent collectivelythe Positive Acknowledge (“ACK”) and the Negative Acknowledge (“NACK”)or (“NAK”). ACK means that a TB is correctly received while NAK means aTB is erroneously received.

In mobile communication networks, a Network Slice Selection Policy(“NSSP”) is used to associate one or more application identities withone or more Single-Network Slice Selection Assistance Information(“S-NSSAI”). An S-NSSAI essentially identifies a certain network slicein the 5G network that should be used to carry the traffic of theassociated application. The NSSP includes a plurality of NSSP rules,each NSSP rule associating an application identity with one or moreS-NSSAIs (e.g., network slices). Conventionally, this policy is manuallyconstructed by the operator. However, manual NSSP construction iscumbersome and time consuming as the operator needs to consider manydifferent applications and manually assign each one of them to one ormore S-NSSAIs.

BRIEF SUMMARY

Methods for creating a NSSP rule based on an application identifier andcorresponding application profile and application provider aredisclosed. Apparatuses and systems also perform the functions of themethods. One method for creating a NSSP rule based on an applicationidentifier and corresponding application profile and applicationprovider includes receiving a first request from a network function anddetermining one or more network slice identifiers associated with eachapplication identifier in the list of application identifiers. Here, thefirst request includes a list of application identifiers and for eachapplication identifier a corresponding application profile and acorresponding application provider. The one or more network sliceidentifiers are determined based on the corresponding applicationprofile and on the corresponding application provider of the applicationidentifier. In some embodiments, the method also includes creating aNSSP rule for each application identifier in the list of applicationidentifiers, the NSSP rule containing the application identifier and theassociated one or more network slice identifiers.

One system for creating a NSSP rule based on an application identifierand corresponding application profile and application provider includesa network exposure function (“NEF”) for a mobile communication networkand a unified data management (“UDM”) node. Here, the UDM node receivesa first request from the NEF, wherein the first request includes a setof one or more application identifiers and, for each applicationidentifier, a corresponding application profile and a correspondingapplication provider. The UDM node determines one or more network sliceidentifiers associated with each identified application based on thecorresponding application profile and on the corresponding applicationprovider of each application identifier. The UDM node also creates aNSSP rule for each application identifier in the set of one or moreapplication identifiers, the NSSP rule containing the applicationidentifier and the associated one or more network slice identifiers.

BRIEF DESCRIPTION OF THE DRAWINGS

A more particular description of the embodiments briefly described abovewill be rendered by reference to specific embodiments that areillustrated in the appended drawings. Understanding that these drawingsdepict only some embodiments and are not therefore to be considered tobe limiting of scope, the embodiments will be described and explainedwith additional specificity and detail through the use of theaccompanying drawings, in which:

FIG. 1 is a schematic block diagram illustrating one embodiment of awireless communication system for creating a NSSP rule based on anapplication identifier and corresponding application profile andapplication provider;

FIG. 2 is a block diagram illustrating one embodiment of a networkprocedure for creating a NSSP rule based on an application identifierand corresponding application profile and application provider;

FIG. 3 is a schematic block diagram illustrating one embodiment of anetwork function apparatus for creating a NSSP rule based on anapplication identifier and corresponding application profile andapplication provider;

FIG. 4 is a schematic block diagram illustrating one embodiment of a setof application profiles used for creating a NSSP rule based on anapplication identifier and corresponding application profile andapplication provider and;

FIG. 5 is a schematic flow chart diagram illustrating one embodiment ofa method for creating a NSSP rule based on an application identifier andcorresponding application profile and application provider.

DETAILED DESCRIPTION

As will be appreciated by one skilled in the art, aspects of theembodiments may be embodied as a system, apparatus, method, or programproduct. Accordingly, embodiments may take the form of an entirelyhardware embodiment, an entirely software embodiment (includingfirmware, resident software, micro-code, etc.) or an embodimentcombining software and hardware aspects.

For example, the disclosed embodiments may be implemented as a hardwarecircuit comprising custom very-large-scale integration (“VLSI”) circuitsor gate arrays, off-the-shelf semiconductors such as logic chips,transistors, or other discrete components. The disclosed embodiments mayalso be implemented in programmable hardware devices such as fieldprogrammable gate arrays, programmable array logic, programmable logicdevices, or the like. As another example, the disclosed embodiments mayinclude one or more physical or logical blocks of executable code whichmay, for instance, be organized as an object, procedure, or function.

Furthermore, embodiments may take the form of a program product embodiedin one or more computer readable storage devices storing machinereadable code, computer readable code, and/or program code, referredhereafter as code. The storage devices may be tangible, non-transitory,and/or non-transmission. The storage devices may not embody signals. Ina certain embodiment, the storage devices only employ signals foraccessing code.

Any combination of one or more computer readable medium may be utilized.The computer readable medium may be a computer readable storage medium.The computer readable storage medium may be a storage device storing thecode. The storage device may be, for example, but not limited to, anelectronic, magnetic, optical, electromagnetic, infrared, holographic,micromechanical, or semiconductor system, apparatus, or device, or anysuitable combination of the foregoing.

More specific examples (a non-exhaustive list) of the storage devicewould include the following: an electrical connection having one or morewires, a portable computer diskette, a hard disk, a random-access memory(“RAM”), a read-only memory (“ROM”), an erasable programmable read-onlymemory (“EPROM” or Flash memory), a portable compact disc read-onlymemory (“CD-ROM”), an optical storage device, a magnetic storage device,or any suitable combination of the foregoing. In the context of thisdocument, a computer readable storage medium may be any tangible mediumthat can contain, or store a program for use by or in connection with aninstruction execution system, apparatus, or device.

Reference throughout this specification to “one embodiment,” “anembodiment,” or similar language means that a particular feature,structure, or characteristic described in connection with the embodimentis included in at least one embodiment. Thus, appearances of the phrases“in one embodiment,” “in an embodiment,” and similar language throughoutthis specification may, but do not necessarily, all refer to the sameembodiment, but mean “one or more but not all embodiments” unlessexpressly specified otherwise. The terms “including,” “comprising,”“having,” and variations thereof mean “including but not limited to,”unless expressly specified otherwise. An enumerated listing of itemsdoes not imply that any or all of the items are mutually exclusive,unless expressly specified otherwise. The terms “a,” “an,” and “the”also refer to “one or more” unless expressly specified otherwise.

Furthermore, the described features, structures, or characteristics ofthe embodiments may be combined in any suitable manner. In the followingdescription, numerous specific details are provided, such as examples ofprogramming, software modules, user selections, network transactions,database queries, database structures, hardware modules, hardwarecircuits, hardware chips, etc., to provide a thorough understanding ofembodiments. One skilled in the relevant art will recognize, however,that embodiments may be practiced without one or more of the specificdetails, or with other methods, components, materials, and so forth. Inother instances, well-known structures, materials, or operations are notshown or described in detail to avoid obscuring aspects of anembodiment.

Aspects of the embodiments are described below with reference toschematic flowchart diagrams and/or schematic block diagrams of methods,apparatuses, systems, and program products according to embodiments. Itwill be understood that each block of the schematic flowchart diagramsand/or schematic block diagrams, and combinations of blocks in theschematic flowchart diagrams and/or schematic block diagrams, can beimplemented by code. This code may be provided to a processor of ageneral-purpose computer, special purpose computer, or otherprogrammable data processing apparatus to produce a machine, such thatthe instructions, which execute via the processor of the computer orother programmable data processing apparatus, create means forimplementing the functions/acts specified in the schematic flowchartdiagrams and/or schematic block diagrams.

The code may also be stored in a storage device that can direct acomputer, other programmable data processing apparatus, or other devicesto function in a particular manner, such that the instructions stored inthe storage device produce an article of manufacture includinginstructions which implement the function/act specified in the schematicflowchart diagrams and/or schematic block diagrams.

The code may also be loaded onto a computer, other programmable dataprocessing apparatus, or other devices to cause a series of operationalsteps to be performed on the computer, other programmable apparatus, orother devices to produce a computer implemented process such that thecode which execute on the computer or other programmable apparatusprovide processes for implementing the functions/acts specified in theschematic flowchart diagrams and/or schematic block diagram.

The schematic flowchart diagrams and/or schematic block diagrams in theFigures illustrate the architecture, functionality, and operation ofpossible implementations of apparatuses, systems, methods, and programproducts according to various embodiments. In this regard, each block inthe schematic flowchart diagrams and/or schematic block diagrams mayrepresent a module, segment, or portion of code, which includes one ormore executable instructions of the code for implementing the specifiedlogical function(s).

It should also be noted that, in some alternative implementations, thefunctions noted in the block may occur out of the order noted in theFigures. For example, two blocks shown in succession may, in fact, beexecuted substantially concurrently, or the blocks may sometimes beexecuted in the reverse order, depending upon the functionalityinvolved. Other steps and methods may be conceived that are equivalentin function, logic, or effect to one or more blocks, or portionsthereof, of the illustrated Figures.

The description of elements in each figure may refer to elements ofproceeding figures. Like numbers refer to like elements in all figures,including alternate embodiments of like elements.

In order to automatically construct the NSSP in a 5G mobile network, andto easily manage the NSSP and its distribution, a data management node,such as an UDM, receives a request to set a policy rule relating tonetwork slice selection. In some embodiments, the request is receivedvia a network exposure function (“NEF”). Here, the NEF may receive arequest from a third-party application function (“AF”) associated withone or more application utilized by a UE, where the AF requests to mapan application supported by the AF with one of a set of predeterminedapplication profiles and with a specific application provider. The NEFformats the received request and sends the formatted request to the UDMas a request to set a policy rule relating to network slice selection.In other embodiments, the UDM receives the request to set a policy rulerelating to network slice selection directly from an AF.

Upon receiving the request to set a policy rule relating to networkslice selection, the data management node (e.g., UDM) selects one ormore network slices to be associated with the application based on theapplication's associated application profile and application provider.The data management node creates a NSSP rule associating the applicationwith one or more network slices. In certain embodiments, the datamanagement node identifies one or more UEs associated with theapplication and thus affected by the created NSSP rule. The datamanagement mode may also coordinate with one or more policy controlfunctions to update the NSSP of any affected UEs.

FIG. 1 depicts a wireless communication system 100 for creating a NSSPrule based on an application identifier and corresponding applicationprofile and application provider, according to embodiments of thedisclosure. In one embodiment, the wireless communication system 100includes remote units 105, base units 110, and communication links 115.Even though a specific number of remote units 105, base units 110, andcommunication links 115 are depicted in FIG. 1 , one of skill in the artwill recognize that any number of remote units 105, base units 110, andcommunication links 115 may be included in the wireless communicationsystem 100.

In one implementation, the wireless communication system 100 iscompliant with the LTE system specified in the 3GPP specifications. Moregenerally, however, the wireless communication system 100 may implementsome other open or proprietary communication network, for example,WiMAX, among other networks. The present disclosure is not intended tobe limited to the implementation of any particular wirelesscommunication system architecture or protocol.

In one embodiment, the remote units 105 may include computing devices,such as desktop computers, laptop computers, personal digital assistants(“PDAs”), tablet computers, smart phones, smart televisions (e.g.,televisions connected to the Internet), smart appliances (e.g.,appliances connected to the Internet), set-top boxes, game consoles,security systems (including security cameras), vehicle on-boardcomputers, network devices (e.g., routers, switches, modems), or thelike. In some embodiments, the remote units 105 include wearabledevices, such as smart watches, fitness bands, optical head-mounteddisplays, or the like. Moreover, the remote units 105 may be referred toas subscriber units, mobiles, mobile stations, users, terminals, mobileterminals, fixed terminals, subscriber stations, UE, user terminals, adevice, or by other terminology used in the art. The remote units 105may communicate directly with one or more of the base units 110 viauplink (“UL”) and downlink (“DL”) communication signals. Furthermore,the UL and DL communication signals may be carried over thecommunication links 115.

Each remote unit 105 includes at least one mobile application 108 thatcan communicate with an application function (“AF”) 155 in the datanetwork 150 via a data path 125. In some embodiments, the data path 125is the data path of a PDU session established over one of the multiplenetwork slices 138 supported by the mobile core network 310. Thespecific network slice 138 used by the PDU session is determined by theS-NSSAI attribute of the PDU session. Here, the remote unit 105 isprovisioned with a NSSP which it uses to determine how to route thetraffic of the mobile application 108. The mobile application 108 in theremote unit 105 may also communicate with other application functions155. While a specific number of mobile applications 108 and applicationfunctions 155 are depicted in FIG. 1 , one of skill in the art willrecognize that any number of mobile applications 108 may be included inthe remote unit 105 and any number of application functions 155 may beincluded in the wireless communication system 100.

The base units 110 may be distributed over a geographic region. Incertain embodiments, a base unit 110 may also be referred to as anaccess terminal, a base, a base station, a Node-B, an eNB, a gNB, a HomeNode-B, a relay node, a femtocell, an access point, a device, or by anyother terminology used in the art. The base units 110 are generally partof an access network 120, such as a radio access network (“RAN”), thatmay include one or more controllers communicably coupled to one or morecorresponding base units 110. These and other elements of the accessnetwork 120 are not illustrated but are well known generally by thosehaving ordinary skill in the art. The base units 110 connect to themobile core network 130 via the access network 120. The access network120 and mobile core network 130 may be collectively referred to hereinas a “mobile network” or “mobile communication network.”

The base units 110 may serve a number of remote units 105 within aserving area, for example, a cell or a cell sector via a wirelesscommunication link. The base units 110 may communicate directly with oneor more of the remote units 105 via communication signals. Generally,the base units 110 transmit downlink (“DL”) communication signals toserve the remote units 105 in the time, frequency, and/or spatialdomain. Furthermore, the DL communication signals may be carried overthe communication links 115. The communication links 115 may be anysuitable carrier in licensed or unlicensed radio spectrum. Thecommunication links 115 facilitate communication between one or more ofthe remote units 105 and/or one or more of the base units 110.

In one embodiment, the mobile core network 130 is a 5G core (“5GC”),which may be coupled to a data network 150, like the Internet andprivate data networks, among other data networks. In some embodiments,the remote units 105 communicate with an application function (“AF”) 155(external to the mobile core network 13) via a network connection withthe mobile core network 130. Each mobile core network 130 belongs to asingle public land mobile network (“PLMN”). The present disclosure isnot intended to be limited to the implementation of any particularwireless communication system architecture or protocol. For example,other embodiments of the mobile core network 130 include an enhancedpacket core (“EPC”) or a Multi-Service Core as describe by the BroadbandForum (“BBF”).

The mobile core network 130 includes several network functions (“NFs”)and multiple network slices 138. As depicted, the mobile core network130 includes at least one unified data management with an internal userdata repository (“UDM/UDR”) 132, at least one policy control function(“PCF”) 134, at least one access and mobility management function(“AMF”) 136, and at least one network exposure function (“NEF”) 137.Although a specific number of NFs are depicted in FIG. 1 , one of skillin the art will recognize that any number of NFs may be included in themobile core network 130. In certain embodiments, each of the multiplenetwork slices 138 includes its own dedicated network functions (notshown), such as a session management function (“SMF”) and user planefunction (“UPF”).

The UDM/UDR 132 comprises a Unified Data Management (“UDM”) and itsinternal component User Data Repository (“UDR”). The UDR holdssubscription data including policy data. Specifically, the policy datastored by the UDM/UDR 132 includes the NSSP. The UDM/UDR 132, PCF 134,AMF 136, and SMF (not shown) are examples of control plane networkfunctions of the mobile core network 130. Control plane networkfunctions provide services such as UE registration, UE connectionmanagement, UE mobility management, session management, and the like. Incontrast, a user plane function (UPF) provides data transport servicesto the remote units 105.

The NEF 137 implements a “front end” service that interfaces withexternal application functions and exposes to these functions thecapabilities of the mobile core network. For example, the NEF 137 can beused by an AF 155 to send a message to a group of remote units 105, todiscover the location of a remote unit 105, to charge a certain remoteunit 105, and the like. Thus, the NEF provides a single point of contactfor external applications that want to utilize the services offered bythe internal network functions of the mobile network (e.g., services ofthe AMF 136, PCF 134, UDM 132, SMF, etc.).

The multiple network slices 138 are logical networks within the mobilecore network 130. The network slices 138 are partitions of resourcesand/or services of the mobile core network 130. Different network slices138 may be used to meet different service needs (e.g., latency,reliability, and capacity). Examples of different types of networkslices 138 include enhanced mobile broadband (“eMBB”), massivemachine-type communication (“mMTC”), and ultra-reliability and lowlatency communications (“URLLC”). A mobile core network 130 may includemultiple network slice instances of the same network slice type.Different network slice instance of the same type may be distinguishedby a slice “tenant” (also known as “slice differentiator”) associatedwith the instance.

As discussed above, a mobile application 108 running on the remote unit105 communicates with the AF 155 via the data path 125 that passesthrough a network slice 138 of the mobile core network. Additionally,the AF 155 can send information to the mobile core network 130 which canbe used to optimize the network internal configuration or networkbehavior. In certain embodiments, the AF 155 is an application server(“AS”) or a service capability server (“SCS”) enabling a mobileapplication 108 to access and use functionality provided by the serverover standardized interfaces (e.g., APIs).

The wireless communication system 100 is capable of automaticallyconstructing an NSSP rule for a mobile application 108 and to providethis rule to an affected remote unit 105. The NSSP rule indicates whichS-NSSAI(s) is to be used for transferring the traffic of the mobileapplication 108. The NSSP is constructed and stored in the 5G mobilenetwork and can be sent to a remote unit 105 via the N1 interface (e.g.,the logical connection between the remote unit 105 and the AMF 136).Although the NSSP could be the same for all remote units 105 in thewireless communication system 100, in some embodiments each remote unit105 may have its own NSSP. Here, a NSSP may be constructed byaggregating the NSSP rules applicable to the particular remote unit 105.For example, certain NSSP rules may only be applicable to certain types(or classes) of remote devices, only to certain subscription levels,only to subscribers of certain services, and the like.

An example NSSP with three rules is shown in the following table:

TABLE 1 Prioritized list of associated Application Identity S-NSSAIsRule 1 OS = Android, ID = S-NSSAI-1 = remote.sensing.carmaker[“automotive”, “CarMaker”] Rule 2 OS = Android, ID = S-NSSAI-1 =com.cast.webvideo [“mobile broadband”, *] Rule 3 OS = Android, ID =S-NSSAI-1 = [“iot”, “Lenovo”], gps.phone.tracker.lenovo S-NSSAI-2 =[“iot”, *], S-NSSAI-3 = [“mobile broadband”, *]

In the above table, the first NSSP rule indicates that the traffic ofAndroid application “remote.sensing.carmaker” is to be sent over a PDUsession established with 5-NSSAI=[“automotive”, “CarMaker”]. Here, theS-NSSAI includes two parameters: a slice type (e.g., “automotive”) and aslice tenant (e.g., “CarMaker”). Accordingly, a PDU session with thisS-NSSAI will have a data path 125 that goes through a network slice 138which serves the CarMaker automotive applications.

The second NSSP rule indicates that the traffic of Android application“com.cast.webvideo” is to be sent over a PDU session established withS-NSSAI=[“mobile broadband”, *], where “*” is a wildcard indicating thatany network slice 138 that supports the “mobile broadband” traffic typeis suitable for sending/receiving traffic of Android application“com.cast.webvideo”. The third NSSP rule indicates that traffic ofAndroid application “gps.phone.tracker.lenovo” is to be sent over a PDUsession established with one of the following S-NSSAIs: [“iot”,“Lenovo”], [“iot”, *], or [“mobile broadband”, *]. In the third NSSPrule, the S-NSSAIs are given in a prioritized list such that the remoteunit 105 first attempts to send traffic for “gps.phone.tracker.lenovo”over a network slice 138 that supports the “IoT” traffic type andbelonging to the tenant “Lenovo”. Should such a PDU session be unable tobe established, then the remote unit 105 next attempts to send trafficover another network slice 138 that supports the “IoT” traffic type.Finally, should a PDU session with an IoT-type network slice 138 beunable to be established, then the remote unit 105 attempts to sendtraffic over a PDU session established the network slice 138 thatsupports the “mobile broadband” traffic type.

When the remote unit 105 receives the NSSP, it uses the NSSP todetermine how to route the traffic of its mobile applications 108.Specifically, the remote unit 105 routes the traffic of a mobileapplication 108 over a PDU session that matches one of the S-NSSAIsassociated with the mobile application 108 according to the NSSP. Forexample, when the application “com.cast.webvideo” requests datacommunication, according to the NSSP shown in the table above, theremote unit 105 routes the traffic of this application over a PDUsession with S-NSSAI=[“mobile broadband”, *]. If the remote unit 105 hasno active PDU session with this S-NSSAI, the remote unit 105 requeststhe establishment of a new PDU session with S-NSSAI=[“mobile broadband”,*].

In order to automatically construct a NSSP rule, an AF 155 associatedwith a particular mobile application 108 sends a request to the mobilecore network 130 to map the particular mobile application 108 to anetwork slice 138 matching a predetermined application profile. Here,the operator of the mobile core network 130 and the operator of the AF155 have previously established an agreement enabling the AF 155 toestablish an authenticated connection with the mobile core network 130(e.g., to the NEF 137) and utilize the services exposed by the NEF 137.

Additionally, the operator of the mobile core network 130 provides tothe operator of the AF 155 a list of supported application profiles.Each mobile application 108 supported by the AF 155 can then be matchedwith one of the supported application profiles based on the trafficcharacteristics of the mobile application 108 and/or based on the typeof mobile application 108. Application profiles are discussed in greaterdetail with reference to FIG. 4 . Based on the application and itscorresponding application profile, the mobile core network 130 (e.g.,the UDM/UDR 132) maps the applications identity to at least one networkslice 138 (e.g., to specific S-NSSAI(s)) to create the NSSP rule.

FIG. 2 depicts a network procedure 200 for creating a NSSP rule based onan application identifier and corresponding application profile andapplication provider, according to embodiments of the disclosure. Thenetwork procedure 200 involves an AF 205, and NEF 210, a UDM 215, a PCF220, and AMF 225, and the UE 230. The AF 205 may be one embodiment ofthe AF 155, the NEF 210 may be one embodiment of the NEF 137, and theUDM 215 may be one embodiment of the UDM/UDR 132 described above withreference to FIG. 1 . The PCF 220 and AMF 225 may be embodiments of thePCF 134 and AMF 136 described above. Additionally, the UE 230 may be oneembodiment of the remote unit 105 described above.

The description below is based on the following example scenario: Eachautomobile made by manufacturer “CarMaker” is equipped with acommunication device (e.g., a UE). This device runs the Androidoperating system and has (i) a telemetry application that collects carsensor data which are sent to CarMaker's data center (ApplicationFunction; AF) and (ii) several other applications used for the in-carentertainment system, e.g., navigation apps, video streaming apps, webbrowsing apps, etc. All UEs in CarMaker cars should receive an NSSPpolicy which maps the telemetry application to a specific S-NSSAI-1 andall other applications to S-NSSAI-2. Instead of configuring this NSSPpolicy manually in the 5G network, the network procedure 200 creates theNSSP automatically after receiving a request from CarMaker's AF anddistributes the NSSP to all applicable UEs.

The network procedure 200 begins with the AF 205 mapping a mobileapplication it supports to one of the predetermined application profilesprovided by the mobile network operator (see block 235). Where the AF205 supports multiple mobile applications, the AF 205 maps each mobileapplication to a predetermined application profile. For example, wherethe AF 205 supports the mobile application “remote.sensing.carmaker”,the AF 205 may map this mobile application to a telemetry-typeapplication profile.

After mapping the mobile applications to application profiles, the AF205 sends a request to the NEF 210, depicted here as a “Set App ProfileRequest” (see messaging 240). After establishing a secure connectionwith the NEF 210, the AF 205 sends the Set App Profile Request whichrequests that the mobile network associate an application supported byAF (i) with a certain application profile and (ii) with a certainapplication provider. In one embodiment, the Set App Profile Request mayinclude a set of one or more tuples, each tuple comprising anapplication identifier, a corresponding application profile, and acorresponding application provider. In another embodiment, the Set AppProfile Request includes (a) a list of application identifiers, (b) alist of application profiles and (c) a list of application providers,and each application identifier in the list of application identifiersis associated with an application profile contained in the list ofapplication profiles and with an application provider contained in thelist of application providers.

Using the above example, the AF 205 may request that the mobileapplication “remote.sensing.carmaker” be associated with a specifictelemetry-type application profile and also associated with theapplication provider “CarMaker.” In certain embodiments, the Set AppProfile Request may omit the application provider parameter where thisparameter can be implicitly derived. For example, if the AF 205 isassociated only with a single application provider (e.g., based on theagreement with the mobile network operator), then the applicationprovider may be omitted.

In some embodiments, the Set App Profile Request also includes theidentity of one or more UEs affected by the requested association. TheSet App Profile Request may include UE parameter containing the identityof a single UE, the identities of multiple UEs, or a UE group identity.Where no UE parameter is included, the NEF 210 may interpret the Set AppProfile Request as affecting all UEs in the mobile network or,alternatively, as affecting only UEs associated with the identifiedapplication provider (e.g. based on subscription). For example, if theapplication provider is “CarMaker” the UEs associated with thisapplication provider are all UEs in automobiles associated with (e.g.,made by) the entity “CarMaker”.

In certain embodiments, when the Set App Profile Request includes theidentity of a single UE, or the identities of multiple UEs, each one ofthese identities is an External Identity, such as an MSISDN identity,used by the AF 205 and the mobile network (e.g., UDM 215) to identify aspecific subscriber of the mobile network. For example, when the UE 230registers with the AF 205, or contacts the AF 205 for the first time,the UE 230 sends its MSISDN identity to the AF 205. In this way, the AF205 becomes aware of the MSISDN identities of one or more UEs thatutilize the considered application.

In certain embodiments, the Set App Profile Request includes a UE groupidentity which is an identity pre-agreed between the mobile networkoperator and the AF operator. The UE group identity may refer to allsubscribers/UEs associated with the identified application (e.g. all UEsin CarMaker cars or all UEs manufactured by Lenovo).

The NEF issues a “Policy Update Request” to UDM which requests to updatethe policy data of a single UE or of a group of UEs (see messaging 245).Here, the NEF 210 formats the AF 205 request into a Policy UpdateRequest which it sends to the UDM 215. The contents of the Policy UpdateRequest are substantially the same as the contents of the Set AppProfile Request. Where the Set App Profile Request omits the applicationprovider, the NEF 210 may add the application provider parameter to thePolicy Update Request.

For each application identifier, the UDM 215 determines one or moreS-NSSAI to associate with the application identifier (see block 250).Based on the received Application Profile ID and Application Provider,the UDM 215 determines an S-NSSAI or a prioritized list of S-NSSAIs thatcan be associated with the identified application. Where multipleS-NSSAIs are associated with the application identifier, the UDM 215 mayfurther determine the order in which a UE is to attempt to use theS-NSSAIs, thereby forming the prioritized list.

The S-NSSAIs determined in response to the Policy Update Request arereferred to herein as the “associated S-NSSAIs”. The associated S-NSSAIsmay be determined either by UDM 215 alone or in association with othernetwork elements (e.g. a Network Slice Selection Function, “NSSF”). Incertain embodiments, a single application profile may correspond tomultiple S-NSSAIs. In other embodiments, a single application profilecorresponds only to a single S-NSSAI. Further, several applicationprofiles may correspond to a single-NSSAI.

After associating the application identifier with an S-NSSAI, the UDM215 constructs a generic NSSP rule for the identified application (seeblock 255). For example, this NSSP rule can contain:App-Identifier=remote.sensing.carmaker, S-NSSAI-1=[“automotive”,“CarMaker”], S-NSSAI-2=[“automotive”, “*”]. The S-NSSAI-1 and theS-NSSAI-2 are to two S-NSSAIs associated with the application withidentity “remote.sensing.carmaker” and the S-NSSAI-1 has the highestpriority.

In response to creating a new NSSP rule, the UDM 215 identifies one ormore UEs affected by the new rule (see block 260). The UDM 215identifies the affected UEs based on the UE identities included in thePolicy Update Request. If the Policy Update Request includes no UEidentities, then the affected UEs are derived based on the applicationprovider. For example, the mobile network may be configured to associateone or more UEs with a certain application provider, in which case, ageneric NSSP rule created above for this application provider affectsall these UEs.

For each affected UE, the UDM 215 checks if the associated S-NSSAIs areincluded in the list of subscribed S-NSSAIs of this UE. As used here,the list of subscribed S-NSSAIs refers to those S-NSSAIs the UE ispermitted to access (e.g., based on the UE's subscriber data). If anassociated S-NSSAI is not included in the list of subscribed S-NSSAIs ofa UE, then the UDM 215 determines whether network policy allows the AF205 to cause changes in the subscription data of this UE. Where the AF205 is permitted to cause changes, then the associated S-NSSAI(s) notincluded in the list of subscribed S-NSSAIs is added in the list ofsubscribed S-NSSAIs for this UE. However, if the AF 205 is not allowedto cause changes in the subscription data of this UE, then theassociated S-NSSAI(s) not included in the list of subscribed S-NSSAIsare removed from the list of associated S-NSSAIs for the UE.

For example, if the UDM 215 determines two associated S-NSSAIs for theapplication “remote.sensing.carmaker” (S-NSSAI-1=[“automotive”,“CarMaker”] and S-NSSAI-2=[“automotive”, “*”]), but S-NSSAI-1 is notincluded in the list of subscribed S-NSSAIs for the UE 230 and cannot beadded to this list based on network policy, then the NSSP rule for theUE 230 would contain only the S-NSSAI-2 that is included in the list ofsubscribed S-NSSAIs for the UE 230. Here, the resulting NSSP rule forthe UE 230 contains the application identity “remote.sensing.carmaker”and the network slice identity S-NSSAI-2. Otherwise, if S-NSSAI-1 can beadded to the list, then the resulting NSSP rule for the UE 230 containsthe application identity “remote.sensing.carmaker” and the network sliceidentities S=NSSAI-1 and S-NSSAI-2.

In certain embodiments, if the UDM 215 changes the list of subscribedS-NSSAIs for the UE 230, the UDM 215 may also update the AMF 225 servingthe UE 230 with the new list of subscribed S-NSSAIs. This can be done byinitiating a subscription data update procedure towards the AMF 225serving the UE 230.

In response to identifying one or more UEs affected by the new NSSPrule, the UDM 215 updates the NSSP of the affected UEs with the new NSSPrule (see block 265). The UDM 215 sends an acknowledgment message to theNEF 210, which in turn sends an acknowledgment message to the AF 205(see messaging 270). Where a new (generic) NSSP rule is successfullycreated, the acknowledgment message contains a positive acknowledgement(“ACK”). In some embodiments, a new generic NSSP rule may not becreated, for example due to subscription limitations. Here, theacknowledgement message contains a negative acknowledgement (“NAK”). Incertain embodiments, the acknowledgement message containing a NAK mayalso include a reason code indicating why the new generic NSSP rule wasnot created. In other embodiments, the acknowledgement message containsNAK when the NSSP of the UE contained in message 245 cannot be updated.

After updating the NSSPs of one or more affected UEs, the UDM 215identifies one or more PCFs which have subscribed to receivenotifications when a UE's policy changes (see block 275). Here, thePCF(s) may subscribe with the UDM 215 to receive policy updates for oneor more of the affected UEs. For example, the PCF 220 may subscribe withthe UDM 215 to receive policy updates for the UE 230 when the UE 230registers with the mobile network.

Here the UDM 215 identifies that the NSSP of the UE 230 has changed andthat the PCF 220 serves the UE 230. The UDM 215 then notifies the PCF220 of the updated NSSP (see messaging 280). The UDM sends a notifymessage to each PCF that is subscribed to receive policy updates for anaffected UE. This message informs the PCF 220 that the NSSP policy ofthe affected UE has been updated. Each affected UE is identified by itsSubscriber Permanent Identity (SUPI).

The PCF 220 forwards the updated NSSP to the AMF 225 which serves the UE230 and the AMF 225 forwards the updated NSSP to the UE 230 over the N1signaling interface (see messaging 285). For example, the PCF 220 mayforward the new NSSP rule created by the UDM 215 towards the UE 230.More generally, each notified PCF forwards the updated NSSP policy toone or more of the affected UEs, e.g. sends to the UE the new NSSP rulecreated by UDM 215. As an example, the new NSSP rule may be included ina NAS Configuration Update command and sent to an affected UE using thenormal N1 signaling procedures. As another example, the NSSP rule may beincluded in a NAS Transport message from the AMF 225 to the UE 230(e.g., in case that the AMF 225 is unaware about the content of theinformation received from the PCF 220).

After receiving the new NSSP rule(s), whenever the mobile application“remote.sensing.carmaker” in the UE 230 requests data communication, theUE 230 transfers data for that application within a PDU session matchingthe S-NSSAI associated with this application (e.g., according to thereceived NSSP rule). Therefore, the data of the mobile application“remote.sensing.carmaker” is transferred via the network slice 138related with this S-NSSAI.

Beneficially, the network procedure 200 avoid the need for deep packetinspection, or similar analysis, of traffic from a mobile application108 to determine a suitable network slice after the UE 230 has alreadysent traffic for this mobile application 108 on a certain PDU session.Rather, the network procedure 200 allows the UDM 215 to automaticallycreate the NSSP using information received by the application provider(e.g., via the AF 205).

FIG. 3 depicts one embodiment of a data management apparatus 300 thatmay be used for creating a NSSP rule based on an application identifierand corresponding application profile and application provider,according to embodiments of the disclosure. The data managementapparatus 300 may be one embodiment of the UDM/UDR 132 and/or the UDM215. Furthermore, the data management apparatus 300 includes a processor305, a memory 310, an input device 315, a display 320, and a transceiver325. In some embodiments, the input device 315 and the display 320 arecombined into a single device, such as a touchscreen. In certainembodiments, the data management apparatus 300 may not include any inputdevice 315 and/or display 320.

The transceiver 325 communicates with other network functions in amobile communication network (e.g., the NEF 137 and/or PCF 134). In oneembodiment, the data management apparatus 300 communicates directly withthe AF 155. In another embodiment, the data management apparatus 300receives communications from the AF 155 via the NEF 127. The transceiver325 may include at least one transmitter 330 and at least one receiver335. Additionally, the transceiver 325 may support at least one networkinterface 340 such as a “N25/Nudr” interface used to communicate with aPCF 134.

The processor 305, in one embodiment, may include any known controllercapable of executing computer-readable instructions and/or capable ofperforming logical operations. For example, the processor 305 may be amicrocontroller, a microprocessor, a central processing unit (“CPU”), agraphics processing unit (“GPU”), an auxiliary processing unit, a fieldprogrammable gate array (“FPGA”), or similar programmable controller. Insome embodiments, the processor 305 executes instructions stored in thememory 310 to perform the methods and routines described herein. Theprocessor 305 is communicatively coupled to the memory 310, the inputdevice 315, the display 320, and the transceiver 325.

In some embodiments, the processor 305 receives a first request from anetwork function. Here, the first request is a policy update request. Inone embodiment, the first request is received from a NEF, such as theNEF 137. As discussed above, the NEF may receive a request to set anapplication profile, wherein the NEF formats this request and sends itto the data management apparatus 300 as the first request.

The first request includes at least a list (or set) of one or moreapplication identifiers and, for each application identifier, both acorresponding application profile and a corresponding applicationprovider. In one embodiment, the first request includes an applicationprovider parameter that indicates an application provider associatedwith the list of application identifiers. In certain embodiments, thefirst request includes an identity of one more UEs affected by the firstrequest. For example, the first request may include a single UEidentifier, a list of multiple UE identifiers, or a UE group identity toindicate which UEs are affected by the request.

In response to the first request, the processor 305 determines one ormore network slice identifiers (e.g., S-NSSAIs) associated with eachapplication identifier in the list of application identifiers. Here, theprocessor 305 selects the one or more network slice identifiers based onthe corresponding application profile and the corresponding applicationprovider of the application identifier. The processor 305 also creates aNSSP rule for each application identifier in the list of applicationidentifiers, the NSSP rule containing the application identifier and theassociated one or more network slice identifiers.

Additionally, the processor 305 may update the NSSP of each of UEaffected by the first request. Here, the NSSP for the UE including oneor more rules for associating an application identifier with one or moresubscribed S-NSSAIs. In some embodiments, the processor 305 updates theNSSP for a UE in the mobile communication network selected based on theassociated one or more network slice identifiers (e.g., S-NSSAIs). Here,updating the NSSP for the UE may include determining whether theassociated one or more S-NSSAIs match the subscribed S-NSSAIs in theNSSP and adding an S-NSSAI of the associated one or more S-NSSAIs to theone or more subscribed S-NSSAIs in response to the S-NSSAI not matchingthe subscribed S-NSSAIs in the NSSP.

In one embodiment, updating the NSSP for the UE further includes theprocessor 305 creating one or more new NSSP rules in the NSSP inresponse to adding an S-NSSAI of the associated one or more S-NSSAIs tothe one or more subscribed S-NSSAIs. In another embodiment, updating theNSSP for the UE further includes the processor 305 initiating asubscription data update procedure in response to adding an S-NSSAI ofthe associated one or more S-NSSAIs to the one or more subscribedS-NSSAIs. Still further the processor 305 may update the NSSP for the UEby identifying a PCF subscribed to receive policy updates for a UEaffected by the first request and notifying the PCF to receive a policyupdate for the UE.

The memory 310, in one embodiment, is a computer readable storagemedium. In some embodiments, the memory 310 includes volatile computerstorage media. For example, the memory 310 may include a RAM, includingdynamic RAM (“DRAM”), synchronous dynamic RAM (“SDRAM”), and/or staticRAM (“SRAM”). In some embodiments, the memory 310 includes non-volatilecomputer storage media. For example, the memory 310 may include a harddisk drive, a flash memory, or any other suitable non-volatile computerstorage device. In some embodiments, the memory 310 includes bothvolatile and non-volatile computer storage media. In some embodiments,the memory 310 stores data relating to creating a NSSP rule based on anapplication identifier and corresponding application profile andapplication provider, for example storing subscriber data, policy data,application identifiers, application profiles, S-NSSAIs, and the like.In some embodiments, the memory 310 also stores program code and relateddata, such as an operating system or other controller algorithmsoperating on the data management apparatus 300 and one or more softwareapplications.

The input device 315, in one embodiment, may include any known computerinput device including a touch panel, a button, a keyboard, a stylus, amicrophone, or the like. In some embodiments, the input device 315 maybe integrated with the display 320, for example, as a touchscreen orsimilar touch-sensitive display. In some embodiments, the input device315 includes a touchscreen such that text may be input using a virtualkeyboard displayed on the touchscreen and/or by handwriting on thetouchscreen. In some embodiments, the input device 315 includes two ormore different devices, such as a keyboard and a touch panel.

The display 320, in one embodiment, may include any known electronicallycontrollable display or display device. The display 320 may be designedto output visual, audible, and/or haptic signals. In some embodiments,the display 320 includes an electronic display capable of outputtingvisual data to a user. For example, the display 320 may include, but isnot limited to, an LCD display, an LED display, an OLED display, aprojector, or similar display device capable of outputting images, text,or the like to a user. As another, non-limiting, example, the display320 may include a wearable display such as a smart watch, smart glasses,a heads-up display, or the like. Further, the display 320 may be acomponent of a smart phone, a personal digital assistant, a television,a table computer, a notebook (laptop) computer, a personal computer, avehicle dashboard, or the like.

In certain embodiments, the display 320 includes one or more speakersfor producing sound. For example, the display 320 may produce an audiblealert or notification (e.g., a beep or chime). In some embodiments, thedisplay 320 includes one or more haptic devices for producingvibrations, motion, or other haptic feedback. In some embodiments, allor portions of the display 320 may be integrated with the input device315. For example, the input device 315 and display 320 may form atouchscreen or similar touch-sensitive display. In other embodiments,the display 320 may be located near the input device 315. As notedabove, in certain embodiments the data management apparatus 300 does notinclude an input device 315 and/or display 320.

The transceiver 325 communicates with network functions in a mobilecommunication network. The transceiver 325 operates under the control ofthe processor 305 to transmit messages, data, and other signals and alsoto receive messages, data, and other signals. For example, the processor305 may selectively activate the transceiver 325 (or portions thereof)at particular times in order to send and receive messages. Thetransceiver 325 may include one or more transmitters 330 and one or morereceivers 335 for communicating with network functions in the mobilecommunication network. As discussed above, the transceiver 325 maysupport one or more the network interfaces 340 for communicating withnetwork functions in the mobile communication network.

FIG. 4 depicts a set 400 of application profiles used for creating aNSSP rule based on an application identifier and correspondingapplication profile and application provider, according to embodimentsof the disclosure. Here, the set 400 includes multiple profile entries405. Each profile entry contains a set index 410 and a profiledefinition 415. As depicted, the profile definition includes anapplication profile ID, an application type, and optionally a trafficcharacteristic, such as a traffic rate parameter or delay parameter. Asdescribed herein, the mobile network operator provides the set 400 ofapplication profiles to an operator of an AF. The AF operator identifiesa best candidate of the profile entries 405 for each mobile applicationit supports. For example, the set index may indicate the order in whichthe AF operator is to consider the application profiles.

FIG. 5 depicts a method 500 for creating a NSSP rule based on anapplication identifier and corresponding application profile andapplication provider, according to embodiments of the disclosure. Insome embodiments, the method 500 is performed by an apparatus, such asthe UDM/UDR 132, the UDM 215, and/or the data management apparatus 300.In certain embodiments, the method 500 may be performed by a processorexecuting program code, for example, a microcontroller, amicroprocessor, a CPU, a GPU, an auxiliary processing unit, a FPGA, orthe like.

The method 500 begins and receives 505 a first request from a networkfunction, the first request including a list (or set) of one or moreapplication identifiers and for each application identifier acorresponding application profile and a corresponding applicationprovider. In some embodiments, receiving 505 the first request from anetwork function includes received the first request from a NEF. Forexample, the NEF may generate the first request from a Set Profilerequest received from an AF, as discussed above with reference to FIG. 2. In certain embodiments, the first request includes an applicationprovider parameter that indicates an application provider associatedwith the list of application identifiers.

In some embodiments, the first request includes an indication of onemore remote units affected by the first request. In certain embodiments,the indication of one more remote units affected by the first requestmay be a single UE identifier, a list of multiple UE identifiers, or aUE group identity.

The method 500 includes determining 510 one or more network sliceidentifiers associated with each application identifier in the list (orset) of application identifiers based on the corresponding applicationprofile and on the corresponding application provider of the applicationidentifier. In certain embodiments, the one or more network sliceidentifiers are one or more single network slice selection assistanceinformation (“S-NSSAIs”).

The method 500 includes creating 515 a NSSP rule for each applicationidentifier in the list (or set) of application identifiers, the NSSPrule containing the application identifier and the associated one ormore network slice identifiers. In some embodiments, creating 515 a NSSPrule includes updating the NSSP of each of the one more remote unitsaffected by the first request. Here, a NSSP for a remote unit includesone or more rules for associating an application identifier with one ormore subscribed S-NSSAIs.

In certain embodiments, creating 515 a NSSP rule includes updating aNSSP for a remote unit in the mobile communication network selectedbased on the associated one or more network slice identifiers. Here,updating the NSSP for the remote unit may include determining whetherthe associated one or more S-NSSAIs match the subscribed S-NSSAIs in theNSSP and adding an S-NSSAI of the associated one or more S-NSSAIs to theone or more subscribed S-NSSAIs in response to the S-NSSAI not matchingthe subscribed S-NSSAIs in the NSSP.

In one embodiment, updating the NSSP for the remote unit furtherincludes creating one or more new NSSP rules in response to adding anS-NSSAI of the associated one or more S-NSSAIs to the one or moresubscribed S-NSSAIs. In another embodiment, updating the NSSP for theremote unit further includes initiating a subscription data updateprocedure in response to adding an S-NSSAI of the associated one or moreS-NSSAIs to the one or more subscribed S-NSSAIs. In certain embodiments,updating the NSSP for the remote unit includes identifying a policycontrol function (“PCF”) subscribed to receive policy updates for theremote unit and notifying the PCF to receive a policy update for theremote unit. The method 500 ends.

Embodiments may be practiced in other specific forms. The describedembodiments are to be considered in all respects only as illustrativeand not restrictive. The scope of the invention is, therefore, indicatedby the appended claims rather than by the foregoing description. Allchanges which come within the meaning and range of equivalency of theclaims are to be embraced within their scope.

The invention claimed is:
 1. An apparatus comprising: a transceiver thatcommunicates with one or more network functions in a mobilecommunication network that supports multiple network slices, eachnetwork slice associated with one or more network slice identifiers; aprocessor that: receives a first request from a network exposurefunction, the first request comprising a list of one or more applicationidentifiers and for each application identifier a correspondingapplication profile and a corresponding application provider; determinesone or more network slice identifiers associated with each applicationidentifier in the list of one or more application identifiers based onthe corresponding application profile and the corresponding applicationprovider of the application identifier; and creates a network sliceselection policy (“NSSP”) rule for each application identifier in thelist of one or more application identifiers, the NSSP rule containingthe application identifier and the associated one or more network sliceidentifiers.
 2. The apparatus of claim 1, wherein the first requestincludes an identity of one more remote units affected by the firstrequest.
 3. The apparatus of claim 2, wherein the identity of one moreremote units affected by the first request is selected from the groupconsisting of: a single user equipment (“UE”) identifier, a list ofmultiple UE identifiers, and a UE group identity.
 4. The apparatus ofclaim 2, wherein the processor updates a route selection policy of eachof the one more remote units affected by the first request.
 5. Theapparatus of claim 1, wherein the processor further updates a routeselection policy for a remote unit in the mobile communication networkbased on the associated one or more network slice identifiers, the routeselection policy for the remote unit comprising one or more rules forassociating an application identifier with one or more subscribed singlenetwork slice selection assistance information (“S-NSSAIs”).
 6. Theapparatus of claim 5, wherein the associated one or more network sliceidentifiers are one or more S-NSSAIs and wherein, to update the routeselection policy for the remote unit, the processor: determines whetherthe associated one or more S-NSSAIs match the one or more subscribedS-NSSAIs in the route selection policy; and adds an S-NSSAI of theassociated one or more S-NSSAIs to the one or more subscribed S-NSSAIsin response to the S-NSSAI not matching the one or more subscribedS-NSSAIs in the route selection policy.
 7. The apparatus of claim 6,wherein, to update the route selection policy for the remote unit, theprocessor creates one or more new NSSP rules in response to adding anS-NSSAI of the associated one or more S-NSSAIs to the one or moresubscribed S-NSSAIs.
 8. The apparatus of claim 6, wherein, to update theroute selection policy for the remote unit, the processor initiates asubscription data update procedure in response to adding an S-NSSAI ofthe associated one or more S-NSSAIs to the one or more subscribedS-NSSAIs.
 9. The apparatus of claim 5, wherein, to update the routeselection policy for the remote unit, the processor identifies a policycontrol function (“PCF”) subscribed to receive policy updates for theremote unit and notifying the PCF to receive a policy update for theremote unit.
 10. The apparatus of claim 1, wherein the apparatuscomprises: a unified data management apparatus; a user data repository;or combinations thereof.
 11. A method comprising: receiving a firstrequest from a network exposure function in a mobile communicationnetwork, the first request comprising a list of one or more applicationidentifiers and, for each application identifier, a correspondingapplication profile and a corresponding application provider, whereinthe mobile communication network supports multiple network slices, eachnetwork slice associated with one or more network slice identifiers;determining one or more network slice identifiers associated with eachapplication identifier in the list of one or more applicationidentifiers based on the corresponding application profile and on thecorresponding application provider of the application identifier; andcreating a network slice selection policy (“NSSP”) rule for eachapplication identifier in the list of one or more applicationidentifiers, the NSSP rule containing the application identifier and theassociated one or more network slice identifiers.
 12. The method ofclaim 11, wherein the first request includes an identity of one moreremote units affected by the first request.
 13. The method of claim 12,wherein the identity of one more remote units affected by the firstrequest is selected from the group consisting of: a single userequipment (“UE”) identifier, a list of multiple UE identifiers, and a UEgroup identity.
 14. The method of claim 12, further comprising updatinga route selection policy of each of the one more remote units affectedby the first request.
 15. The method of claim 11, further comprisingupdating a route selection policy for a remote unit in the mobilecommunication network based on the associated one or more network sliceidentifiers, the route selection policy for the remote unit comprisingone or more rules for associating an application identifier with one ormore subscribed single network slice selection assistance information(“S-NSSAIs”).
 16. The method of claim 15, wherein the associated one ormore network slice identifiers are one or more S-NSSAIs and whereinupdating the route selection policy for the remote unit comprises:determining whether the associated one or more S-NSSAIs match the one ormore subscribed S-NSSAIs in the route selection policy; and adding anS-NSSAI of the associated one or more S-NSSAIs to the one or moresubscribed S-NSSAIs in response to the S-NSSAI not matching the one ormore subscribed S-NSSAIs in the route selection policy.
 17. The methodof claim 16, wherein updating the route selection policy for the remoteunit further comprises creating one or more new NSSP rules in responseto adding an S-NSSAI of the associated one or more S-NSSAIs to the oneor more subscribed S-NSSAIs.
 18. The method of claim 16, whereinupdating the route selection policy for the remote unit furthercomprises initiating a subscription data update procedure in response toadding an S-NSSAI of the associated one or more S-NSSAIs to the one ormore subscribed S-NSSAIs.
 19. The method of claim 15, wherein updatingthe route selection policy for the remote unit comprises identifying apolicy control function (“PCF”) subscribed to receive policy updates forthe remote unit and notifying the PCF to receive a policy update for theremote unit.
 20. A system comprising: a network exposure function(“NEF”) for a mobile communication network that supports multiplenetwork slices, each network slice associated with one or more networkslice identifiers; and a unified data management (“UDM”) node that:receives a first request from the NEF, wherein the first requestcomprises a set of one or more application identifiers and, for eachapplication identifier, a corresponding application profile and acorresponding application provider; determines one or more network sliceidentifiers associated with each identified application based on thecorresponding application profile and on the corresponding applicationprovider of each application identifier; and creates a network sliceselection policy (“NSSP”) rule for each application identifier in theset of one or more application identifiers, the NSSP rule containing theapplication identifier and the associated one or more network sliceidentifiers.